-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(JumpLinks): warned about href and markup/type updates #575
feat(JumpLinks): warned about href and markup/type updates #575
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple non-blocking comments
@@ -16,6 +16,7 @@ export const warningRules = [ | |||
"emptyState-warn-change-structure", | |||
"formControls-updated-markup", | |||
"horizontalSubnav-warn-ariaLabel", | |||
"jumpLinksItem-warn-prop-markup-updates", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if this should really be a warning since the href
now being required will throw build errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that's fair. I'll split that out to its own rule since the markup change should probably still remain a warning.
@@ -0,0 +1 @@ | |||
import { JumpLinksItem } from "@patternfly/react-core"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could these tsx files be deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think they'd be worth keeping in, just so that running the single tests locally we can still check that the output looks as expected (mainly warning vs error). They might be able to be used to create a mass test file where all the rules' input code is rendered to ensure no rules conflict with one another?
Testing it out, though, the single test command throws an error due to no input/output file being found. The script to build the readme also fails without them.
e3232b2
to
c5e7364
Compare
Closes #559